-
Notifications
You must be signed in to change notification settings - Fork 16.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GCS_MAVLink: don't learn a route to the broadcast component #14620
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo
d85ea22
to
6065c72
Compare
Using a component ID of 0 for your source is invalid according to common.xml However, some clients do use it. This stops us learning a route to that client for the broadcast client for our own system ID.
.... even if we've forwarded them to someone else.
6065c72
to
3b833a1
Compare
This PR fixes dataflash-over-mavlink on CubeOrange. The second patch here was required as currently we don't process messages sent to the broadcast system if we've forwarded to any other system - which is wrong. It means if you connect a second GCS on a second telemetry link then we stop processing |
} | ||
if (msg.sysid == mavlink_system.sysid && | ||
msg.compid == mavlink_system.compid) { | ||
// don't learn routes to ourself. We know where we are. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it would be funnier with "We know who we are" :)
Marking this as DevCall in case @lucasdemarchi (owner) doesn't merge it before then :-) |
Using a component ID of 0 for your source is invalid according to
common.xml
However, some clients do use it.
This stops us learning a route to that client for the broadcast client
for our own system ID.